Projected release: April 30, 2025

Proposed changes

Problem: NGINX One is intaking metrics from customer's data planes that can indicate large negative outcomes that must have action taken on them urgently. Such as , NGINX One checks for CVE impacts. All of this information is extremely valuable, but only if the customer is aware of it in a timely enough fashion to take action.

Solution: If user's data-path has impacting CVEs, we proactively notify, so that use can take action to remedy.

Testing: User registers instance in F5 NGINX One console, and is alerted on CVEs impacting instances.

Please focus on (optional):
Please help editing wording.

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

If this PR addresses an issue on GitHub, ensure that you link to it here:

Closes #ISSUE

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md and CHANGELOG.md